Clarify hotpatch rollback instructions#13415
Clarify hotpatch rollback instructions#13415lecoursen merged 5 commits intogithub:mainfrom ThatStoney:patch-2
Conversation
Replication does not need to be stopped before hotpatching, so most customers faced with a rollback will probably have replication running. Since replication can't be running for a package upgrade (which is how we roll back a hotpatch) we should include a reminder in our docs that replication will need to be stopped prior to rolling back.
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
|
Co-authored-by: Vanessa <vgrl@github.com>
|
I'll go ahead and merge this now! |
Replication does not need to be stopped before hotpatching, so most customers faced with a rollback will probably have replication running. Since replication can't be running for a package upgrade (which is how we roll back a hotpatch) we should include a reminder in our docs that replication will need to be stopped prior to rolling back.
Why:
Closes https://github.com/github/docs-content/issues/5897
What's being changed:
Check off the following:
Writer impact (This section is for GitHub staff members only):